Repository navigation
Open sign-up: new accounts go straight to the console (FW-603) - #43
Merged
Merged
Conversation
The service's SIGNUP_MODE is now "open", so whoever signs in uses the console, and accounts that were waiting are let in too. The waitlist stays in the code: setting it back to "waitlist" brings it back. The site stops talking about a waitlist and early access: - The landing page's last section is Get started (#get-started), with "Get started free" for /signup. The header links to it as Sign up (as short as Waitlist was, so the links still fit one row at phone widths), and the footer as Get started. - /pricing says to start on Free and that paid plans aren't billed yet. The Free, Launch and Scale cards say Get started, and the FAQ says you can sign up now. - /signup's lead says the account opens the console again. - The admin page opens on All while sign-up is open, since nobody waits, and Remove's question no longer says the account goes back on the waitlist. The API tests now follow the deployed setting, and the waitlist tests turn the waitlist on themselves. api/README.md says sign-up is open and how to put the waitlist back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 13, 2026
Contributor
|
Landed on preview through #47, which merged this branch together with the other two FW-60x PRs on top of the Paygate billing work. Your commits are unchanged. Changes made during the merge: the profile-name migration is renumbered to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
FW-603: open sign-up. New accounts go straight to the console instead of the waitlist, and the site stops talking about a waitlist or early access.
Service (
api/)SIGNUP_MODEinwrangler.jsoncis now"open". Accounts already waiting get in too."waitlist"brings it back.api/README.mdsays sign-up is open, and how to put the waitlist back.Site
#get-started): "Gate your agents. Start for free.", with a Get started free button to/signupand Sign in for existing accounts./pricing:/signup: the lead goes back to saying the account opens the console.index.htmlnote no longer mentions the waitlist.When it merges
Someone with Cloudflare access needs to redeploy the Worker (
npm --prefix api run deploy). The site changes go out with the preview workflow, but sign-up only opens once the Worker is redeployed. Until then, new accounts still land on/waitlist, even though the copy says they go to the console.Testing
npm --prefix api run check: 57 tests pass.npm --prefix site run checkpasses, anddocs/matches a rebuild./pricing./app, and/waitlistpasses an approved account on to it.SIGNUP_MODEset back to"waitlist": 25 checks pass, so the waitlist still works if it's turned back on.Merging with the other two PRs
This PR, #44 (FW-601, the header sign-in) and #45 (FW-602, the profile name) each rebuild
docs/. Whichever merges second will conflict ondocs/and on one comment line inSiteHeader.tsx, which is resolved by rebuilding. I merged all three locally and ran every check above on the result: everything passes.🤖 Generated with Claude Code